Skip to content

feat: add option to return unmatched logs - #18

Open
hu6r1s wants to merge 1 commit into
SigmaHQ:mainfrom
hu6r1s:feat/unmatched-log
Open

hu6r1s wants to merge 1 commit into
SigmaHQ:mainfrom
hu6r1s:feat/unmatched-log

Conversation

@hu6r1s

@hu6r1s hu6r1s commented Nov 1, 2026

Copy link
Copy Markdown

Summary

This PR adds an option to return logs that do not match any Sigma rules.

Motivation

In some environments, logs need to be inspected for threat intelligence indicators (such as malicious IP addresses) before being processed by the Sigma Engine.

For example:

Logs are parsed and checked against threat intelligence IP lists before being passed to the Sigma Engine.

A log may contain a known malicious IP address, even if it does not match any Sigma rule.

Currently, logs that do not match any Sigma rule are discarded, making it impossible for downstream processing to use those logs to generate threat intelligence events.

This means potentially valuable threat intelligence matches can be lost simply because the log does not match a Sigma rule.

Changes

Add an option to control whether unmatched logs are returned.

Preserve the existing behavior by default.

When enabled, return logs that do not match any Sigma rule, allowing downstream components to process them independently.

Use Case

This allows applications to perform additional detection based on threat intelligence indicators while still using Sigma rules for behavior-based detection.

It also allows downstream systems to handle both Sigma-matched and unmatched logs without losing potentially relevant threat intelligence information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant